JSON Encoded Data

These examples have been formatted for easier reading. Newlines are not required in the actual JSON data.

Single “message” supplied via “values” JSON object:

{ "target": "UID998783",
"code": "mp10",
"time": "2014-07-24T18:47:43Z",
"location": {"latitude":37.795227, "longitude":-122.398828},
"values": {"temp": 98.6, "humidity": 68.2}
}

Multiple “messages” supplied via “values” JSON array of objects. Each of the array elements supplied via the “values” JSON array will generate one message on the server all of which will have the same “time” and “location” values.

{ "target": "UID998783",
"code": "mp10",
"time": "2014-07-24T18:47:43Z",
"location": {"latitude":37.795227, "longitude":-122.398828},
"values": [{"temp": 98.6, "humidity": 68.2}, {"temp": 101.4, "humidity":
70.4}]
}

Message Field Description

target

• Status:
  • Required (see device adapter specific documentation).
• Definition:
  • Unique ID value for this device (Router serial number value)
• Example:
  • UID998783

code

• Status:
  • Required.
• Definition:
  • Unique message ‘code’ value that is used by device adapter to identify the correct directive message definition to be used to process this message
• Example:
  • mp10 This value is defined when you create a “Device Profile” message in your application. The mp10 is only an example of what it could be. This is not the device profile’s code value, but the message within the device profile.

time

• Status:
  • Optional.
• Definition:
  • Time the message was generated.

• Format:

  • XML 8601 format
  • YYYY-MM-DDThh:mm:ss.sTZD Formats (all examples are parsed to the same internal value). Please review http://www.w3.org/TR/xmlschema-2/#isoformats for additional information on valid date/ time formats paying special attention to the info in section “3.2.7 dateTime”.

• Example:

  • 2015-12-03T00:54:51Z
  • 2015-12-03T00:54:51+00:00
  • 2015-12-02T16:54:51-08:00

location

• Status:
  • Optional.
• Definition:
  • The “latitude” and “longitude” contained in the directive message
• Fields within this block:
  • latitude
  • longitude
• Example:
  • {"latitude":37.795227, "longitude":-122.398828} Note: This data object may be left out of the message since it is optional and may not be available or not applicable for stationary device installations.

JSON Message Specific Fields

A JSON object or an array of objects named values will contain one or more JSON values that are to be processed as the message values that correspond to the message identified via the code field value.

values

• Status: supplied when sending a single message.
• Definition: Block that contains field values to be processed for a message.
• Examples:
  • Sending a temperature and humidity value: "values": {"temp": 98.6, "humidity": 68.2}
  • Sending text values: "values": {"tank_level": "low", "pump_psi": 42.53}

values (array)

• Status: supplied instead of the values field. This is a JSON array of objects that contain field values that will result in one message for each array object.
• Example:
  • "values": [{"temp": 98.6, "humidity": 68.2}, {"temp": 101.4, "humidity": 70.4}]

Message Sending Strategies

• Periodic Updates Sending Sensor data (e.g., Temperature and Humidity) on a periodic interval. The block below will be posted via UDP/TCP to Fusion Connect by device on a periodic basis.

  { "target": "UID998783", "code": "mp10", "time": "2014-07-24T18:47:43Z", "location": {"latitude":37.795227, "longitude":-122.398828}, "values": {"temp": 98.6, "humidity": 68.2} }

• Historical Data Snapshot Instead of posting data on a periodic basis – this method allows the user to aggregate data locally on the device and then send the readings in one packet to minimize OTA and data costs. E.g. Collect temperature and humidity readings from the last 60 minutes sampled every 15 minutes and send to Fusion Connect in one packet.

  { "target": "UID998783", "code": "mp10", "time": "2014-07-24T18:47:43Z", "location": {"latitude":37.795227, "longitude":-122.398828}, "values": [ {"temp": 98.9, "humidity": 68.8, "rtime": "2014-07-24T18:00:00Z"}, {"temp": 98.5, "humidity": 68.3, "rtime": "2014-07-24T18:15:00Z"}, {"temp": 97.9, "humidity": 67.8, "rtime": "2014-07-24T18:30:00Z"}, {"temp": 98.6, "humidity": 68.2, "rtime": "2014-07-24T18:45:00Z"}] }

• Alerts/Alarms Sends alert information to Fusion Connect. With smarter devices that have processing capabilities – the device can notify the server when events of interest occur. For example, if a the temperature is greater than 50 degrees, (e.g., Temp > 50), you can send a temperature alarm along with current temperature and humidity information. The information is sent to the server only when the alarm condition is triggered on the device.

  { "target": "UID998783", "code": "mp10", "time": "2014-07-24T18:47:43Z", "location": {"latitude":37.795227, "longitude":-122.398828}, "values": { "temp_alarm": "High", "temp": 98.6, "humidity": 68.2} }